The database upgrade for this version of iMIS 15 implements changes that prevent you from modifying the out-of-the-box iMIS 15 website content. These changes are part of an ongoing progression of improvements to make it easier and safer for your organization to upgrade your websites and content.
In this release, we restructured Manage websites to organize websites into folders that make clear their usage: Core Sites holds essential iMIS applications (such as iMIS Desktop View); be prepared to recreate any customizations you introduce there. Sample Websites holds the growing set of iPart-based sites (Member, Member Mobile); refer to it for comparison, but make no changes. Manage your own sites outside of these folders so that you can change, copy, and implement, safe from overwriting by upgrades.
All content records in the Core Sites and Sample Websites content folders are protected as System content, which includes any content you may have previously created in those folders. After your database is upgraded, if you attempt to save any changes to System content, you will receive an error message that you Cannot modify system content and will not be permitted to save your changes. Currently, you must make a copy of System content in order to make any changes to it, then update any shortcuts or navigation items to point to the new copy.
Before upgrading your database, please consider each of the following scenarios and take the action indicated if the scenario applies to your situation.
■ If you are actively using the out-of-the-box Member Website, then you must create a copy of your version of the website before initiating the database upgrade.
■ If you are actively using the out-of-the-box Mobile Website, then you must create a copy of your version of the website before initiating the database upgrade.
■ If you have created any new content under the @/Member content folder, then you must move that content to a folder that is outside of the @/Member folder (e.g., create a new @/MyContent folder and move your content into it) and publish your content after you move it.
■ If you have created any new content under the @/Mobile content folder you must move that content to a folder that is outside of the @/Mobile folder (e.g., create a new @/MyContent folder and move your content into it) and publish your content after you move it.